<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>programming on Derek Fritz</title>
    <link>/tags/programming/</link>
    <description>Recent content in programming on Derek Fritz</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>MIT</copyright>
    <lastBuildDate>Thu, 25 Mar 2021 00:00:00 +0000</lastBuildDate>
    
        <atom:link href="/tags/programming/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Recent Focuses</title>
      <link>/post/recent-focuses/</link>
      <pubDate>Thu, 25 Mar 2021 00:00:00 +0000</pubDate>
      
      <guid>/post/recent-focuses/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s been a while since I&amp;rsquo;ve posted an update, so I thought I&amp;rsquo;d go ahead and review some of my development goals recently. I&amp;rsquo;ve been investing some time familiarizing myself
with a variety of technologies I&amp;rsquo;m interesting in pursuing long-term. As I strive to become a better web-developer, I aim to build up my skillset of languages and development tools.&lt;/p&gt;
&lt;style&gt;
img {
    display: inline-block;
    margin: 10px;
    vertical-align: middle;
    white-space: nowrap;
}
&lt;/style&gt;
&lt;div id=&#34;icon-banner&#34;&gt;
    &lt;img src=&#34;/images/docker.png&#34; width=&#34;220&#34;&gt;
    &lt;img src=&#34;/images/aws.png&#34; width=&#34;220&#34;&gt;
    &lt;img src=&#34;/images/react.png&#34; width=&#34;200&#34;&gt;
&lt;/div&gt;
&lt;h3 id=&#34;containers&#34;&gt;Containers&lt;/h3&gt;
&lt;p&gt;I love containers. I think they&amp;rsquo;re novel and incredibly effective when applied in the right way. At my current position, we use containerized dev environments to
ensure we always have access to the same resources with the latest updates.&lt;/p&gt;
&lt;p&gt;While I have primarily been a &lt;em&gt;consumer&lt;/em&gt; of containers, I&amp;rsquo;ve been trying to containerize some applications of my own recently. For this, I utilized docker-compose
to configure individual containers for the different layers of my project (build, application, persistence) and then deployed the resulting container images
to AWS ECR (Elastic Container Registry). I was then able to deploy my containers to AWS ECS (Elastic Container Service) in their own Fargate instances.&lt;/p&gt;
&lt;p&gt;This was a great project for me, as it helped me gain a better understanding of not only &lt;em&gt;how to use&lt;/em&gt; containers, but also how to build containers myself.&lt;/p&gt;
&lt;h3 id=&#34;aws&#34;&gt;AWS&lt;/h3&gt;
&lt;p&gt;This has been a big area of study for me recently, as it also pertains to my professional work. I&amp;rsquo;ve worked with several AWS services in the past for small projects, but largely
avoided any complex configurations or multi-service integrations. Lately I&amp;rsquo;ve been focusing on the AWS ecosystem holistically, discovering the common service combinations and
how they communicate with one another.&lt;/p&gt;
&lt;p&gt;Several AWS services I&amp;rsquo;ve been focusing on are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://aws.amazon.com/cloudformation/&#34;&gt;CloudFormation&lt;/a&gt; - A programmatic way to configure and deploy applications (Infrastructure as Code)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://aws.amazon.com/codebuild/&#34;&gt;CodeBuild&lt;/a&gt; - An AWS-managed build service (CI)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://aws.amazon.com/codepipeline/&#34;&gt;CodePipeline&lt;/a&gt; - An AWS-managed deployment service (CD)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://aws.amazon.com/ecs/&#34;&gt;ECS&lt;/a&gt; - A container orchestration service with multiple deployment form factors (I&amp;rsquo;ve focused on Fargate)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://aws.amazon.com/rds/&#34;&gt;RDS&lt;/a&gt; - A fully managed relational database service&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://aws.amazon.com/api-gateway/&#34;&gt;API Gateway&lt;/a&gt; - The &amp;ldquo;front door&amp;rdquo; for your public-facing applications in AWS&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I&amp;rsquo;ve set up some basic applications utilizing these services in AWS to familiarize myself with the standard workflow and integration points. AWS is a &lt;em&gt;giant&lt;/em&gt; ecosystem,
so I hope to continue discovering better ways to leverage the features it provides.&lt;/p&gt;
&lt;h3 id=&#34;react&#34;&gt;React&lt;/h3&gt;
&lt;p&gt;React is obviously immensely popular in the current market, so it&amp;rsquo;s a library I feel is a necessity to become somewhat familiar with at least. I&amp;rsquo;ve used alternative frontend
frameworks, such as Polymer and Vue.js, which have given me some foundational experience to work with.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/images/react-demo.gif&#34; alt=&#34;react demo&#34;&gt;&lt;/p&gt;
&lt;p&gt;I haven&amp;rsquo;t developed anything major with React quite yet, but I have put together a simple form-based webpage with input validation and a mocked call to an external service.
This was a fairly straightforward day-project which gave me insight into how React handles component composition and state management.&lt;/p&gt;
&lt;h3 id=&#34;the-never-ending-process&#34;&gt;The Never-Ending Process&lt;/h3&gt;
&lt;p&gt;Continually learning more about the tools and languages in the industry will always be a goal of mine. At the same, it&amp;rsquo;s impossible to become an expert in every tech stack.
I believe it&amp;rsquo;s important to refresh your knowledge bank every now and then in order to maintain a broad perspective. This can help you approach problems in a more nuanced
and efficient manner than if you specialized in a few areas.&lt;/p&gt;
&lt;p&gt;I plan on continuing my journey toward becoming a wiser web-developer throughout this year, hopefully finding exciting ways to apply my new knowledge and experience. Until next
time, learn something new and stay sharp!&lt;/p&gt;

</description>
    </item>
    
    <item>
      <title>Hello World</title>
      <link>/post/hello-world/</link>
      <pubDate>Thu, 03 Sep 2020 00:00:00 +0000</pubDate>
      
      <guid>/post/hello-world/</guid>
      <description>&lt;p&gt;Clichéd, I know. But it had to be done. As the first post on this site some formalities have to be satisfied, and as a programmer it would be remiss of me not to label them properly.&lt;/p&gt;
&lt;h3 id=&#34;down-to-business&#34;&gt;Down to Business&lt;/h3&gt;
&lt;p&gt;With that out of the way: I’m building this site primarily as an opportunity to educate myself about web design practices. This idea stemmed from my interest in the &lt;a href=&#34;https://jamstack.wtf/&#34;&gt;JAMstack&lt;/a&gt; concept and the beautiful simplicity of it all. I had been meaning to work on a personal site or blog of some sort, and I figured this would be the perfect approach for the time being.&lt;/p&gt;
&lt;p&gt;I may explore the details of the JAMstack in a later post, but it’s essentially an evolution of the static web page. By synthesizing the power of JavaScript, APIs, and Markup (Markdown in this case), JAMstack websites can provide semi-dynamic content while boasting the lightweight benefits of static sites. This also makes them entirely server-less, allowing for accessible deployment and hosting via platforms such as &lt;a href=&#34;https://www.netlify.com/&#34;&gt;Netlify&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I’d like to continue updating this site as I learn more about web design paradigms and discover new ways to leverage the JAMstack. Meanwhile, I plan on occasionally adding a post or two as a form of thought-bank. Maybe I’ll come back in a couple of years to reflect on what I’ve learned since (hopefully enough to feel a little proud 😉).&lt;/p&gt;

</description>
    </item>
    
  </channel>
</rss>
